on the entity having more than one translatable input, reusing the editor's
field-counting logic.

2. Surface a quality badge. When every value is a 100% TM match, the composed
string is a perfect TM match, so return quality 100 and pass it through to
the panel.

3. Render composed (multi-value) suggestions as labeled fields, the same
representation as the original string panel.

across all input fields, reusing the field-building logic that
is already used by the History panel.

The plain message is recorded as `machinery.translation` so that source
attribution still matches the saved translation on submit.

string isn't suggested back to itself. The composed path didn't, so a
composed TM result could be reconstructed from the entity's own
translation after it was translated.

Add an opt-in `exclude_entity` flag to Pretranslation that excludes the
entity's own TM entries from per-value lookups, and enable it from the
Machinery composed view. A value that can only be served by the entity's
own translation then has no TM match, so a TM-only composition relying
on it is no longer produced. Pretranslation behavior is unchanged.

Re-applying a composed Machinery suggestion (or restoring history)
after editing a field took two clicks: the first did nothing.

Typing updates only CodeMirror's internal doc and EditorResult, not
EditorData.state.fields, so TranslationForm doesn't re-render and each
EditField keeps a stale `defaultValue`. EditField re-syncs its document
only in `useEffect(() => setValue(defaultValue), [defaultValue])`.
distributeEntrySource builds new fields with placeholder handles while
the on-screen editors stay bound, via their React key, to the previous
fields' live handles. The re-applied value for the edited field equals
its stale `defaultValue`, so the effect doesn't fire and the field
isn't updated. A later re-render refreshes `defaultValue`, which is why
the second click works.

Push the distributed values straight into the live handles, matched by
field id, the same way clearEditor does, so one click suffices.

The "Refine using AI" dropdown doesn't work on composed (multi-field/
plural) suggestions: the loader never shows, the refined result never
updates the UI, and copying dumps the raw Fluent source into the first
field. The backend /gpt-transform/ endpoint also refines a single
string, so it can't preserve the entry structure (e.g. returns 2 plural
forms instead of 4).

Hide the dropdown for composed suggestions so they behave like a plain
Google Translate source. Proper composed support is left as a follow-up.

When a suggestion combines multiple sources (e.g. GOOGLE TRANSLATE and
TRANSLATION MEMORY), the source titles ran together with no separator.

…ntity.value and .properties represent a single-pattern or multi-pattern message.

value_from_string in pontoon.sync duplicated parse_db_string_to_json. Consolidate into a single parse_source_string_to_json in pontoon.translations (beside
its inverse, serialize_for_db); parse_db_string_to_json now delegates to it, and the key-aware path picks up the MF2 catchall normalization the sync copy was missing.

…cialFormats, which is byte-for-byte identical

…ntity.properties with no parse. Also, document the source-side heuristic.

The composed-machinery gate counted source patterns, so an en-US message with only `*[other]` was treated as single- pattern and skipped — even for locales like Slovenian that need one/two/few/other.

Count target patterns instead: the backend reuses the plural expansion walk_entity() already performs, and the frontend's hasMultipleFields expands plural selectors to the locale's CLDR categories. A single-variant source now composes to a full multi-pattern suggestion for the target locale.